Summary
This file is Radium's way of communicating and responding to people who post messages to the newsgroup "alt.binaries.sounds.utilities.d" (ABSUD).

1. Replys
2. Communication FAQ
3. Radium public PGP key

Replys
from: Rebal 3
Re: Help! Radium Cakewalk 8 invalidated my system HD
I know this was happening to others here about a year back. I had installed it back then without a problem but it got me this time. Does anybody remember a fix and/or an explanation? It would be much appreciated. TIA!

Answer : When Cakewalk 8 came out reports started coming in about how after installing their root directory was cleaned out (autoexec.bat deleted etc). A lot of people said they thought it was the Radium crack or a virus. In fact it was neither : the original will do this as well! Here's the explanation. The installer that TwelveTone made for Cakewalk places some files in the system 'temp' directory, then deletes them all after the installation is done. However they overlooked what would happen if NO temp directory was defined - it would assume the C:\ root was the temp.. and it deletes all files there. We've seen it happen to a horrified original user. Oddly, seems TwelveTone never released a fix for their destructive error. In short, when installing cakewalk always make sure you have a temp dir defined.

from: ukboy
Re: Cubase 3.7 / VST effects
I'm attempting to "trial" Rad's Cubase 3.7 that was recently posted. None of the VST effects except Especial, Neon and DirectX choices show up in the "rack" popup menus. Is there some sort of config thing I've overlooked?

Plugins that are installed before 3.7 don't always get registered and seen. (This one was our fault). Fortunately the fix is fairly simple. Run regedit (c:\windows\regedit.exe) and delete the tree 'HKEY_LOCAL_MACHINE\SOFTWARE\Steinberg\VSTPlugins'. That's it - no need to uninstall, reboot, or anything else. The next time VST is run this tree will be rebuilt and all the plugins should be visible.

Communication FAQ (new or updated text is in red)
Q : Does Radium have email, website or visit chat groups?
A : No

Q : How can someone get a message to Radium?
A : We periodically read messages in the Newgroup ABSUD. (Alt.Binaries.Sounds.Utities.D) Please put 'ATTN Radium :' in the subject line.

Q : How would Radium reply?
A : We will never post replys directly to newsgroups. The only place you will see a Radium reply is in this Radiumchat.htm file that is included with releases. We would be grateful if someone (anyone) would 'repost' each radiumchat.htm file to the absud newsgroup. (We won't be posting it there ourselves for security reasons.) Please post as an html file attachment if possible.

Q : What if the message is private?
A : Use PGP to encode the message. Our public key is at the very end of this radiumchat. **Be sure to also include YOUR public PGP key with any post.** (otherwise we cant read the message or reply to you!):)

Q : If we post our public key wont everyone be able to read the messages?
A : No. Here's a quick intro - When you first run PGP you will be prompted to create a key PAIR (use RSA 2048 for your key.) You will then have a Public and a Private key. To communicate with someone you will both need to know each others PUBLIC key. Other parties wont be able to read it because they don't have your individual PRIVATE keys.

Although we will read every post, our time is limited and we will only be able to reply here occasionally. Also please don't expect replys for questions like 'Where can i get X, When will X be released, etc'

Radium public PGP Key :

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com>

mQENAzeok58AAAEIAOVIGaky9hPj11/NJLbRJyZC5qEUwbmxjaqPEbx9Cv0jCH9s
pL9rAPeM/ekbYwJsxTxko80TZugnWOkfwhJCLrx5NwO/8lE36GKfzeizc5Wf6/dk
DCF8MLChVH31wykxZOCnc0Xyqr2fBQbiuGqqcbqJEtkmP/ile236ioRtBvqhAFaM
voPdju+KEq1ElFRHQ8NmmEtqo+uDnDEicPNaXdGOM0PGw1x4aNeBWY0bFkyZ7e3m
qvltSqwW5cc0w7tRiYUnfJpxJ8gP6A49cpotE+YlGXsuTv0/adNRdwWh7QEb+dcr
4nmUxgGCJquGQCK2PU1toK3Rhr2Ll/q2NxDTFs0ABRG0DHJjaGF0IDxub25lPokB
FQMFEDeok5+X+rY3ENMWzQEBx/gH/jXxolTCI5uUuzCRucBJi5LtOp75HLRQQTe3
+hCqCzAzx7ejGDqx0bOISFSD6M0PFln7aSVYXzeKeM3XSYoyXENAEVLuIlMglQdL
p+JKH5j6MeuMk0Oq+TMarVqGqlEZR7rrqgTo3AXxpTPBucwU9ri6f5pPvm5hc3ke
XsveiV7sGeudXtm+fqXPyRT15jHauDtAkg/Ej5bGPQoYPTVuOcQoppW/zpVA1lCP
+3tFLek4t9XOBtXom+n0YXtTjhBAI6eahLHhtUuEr9OAhd7at7MM+Pl5RlE1dLOf
jUsVamgujO6oLdK846Mk91RBnZ2sGoKI3SmC7TOesGwlpqHmTRg=
=RPpY
-----END PGP PUBLIC KEY BLOCK-----